Methods, base station and user equipment

ABSTRACT

A base station maps a first Transmission Time Interval (TTI) configuration associated with a carrier of a RAN to a first RAN slice. The first RAN slice is configured to support a first Quality of Service (QoS) requirement. The first TTI configuration comprises a first number of Orthogonal Frequency-Division Multiplexing (OFDM) symbols. The base station maps a second TTI configuration associated with the carrier to a second RAN slice. The second RAN slice is configured to support a second QoS requirement different from the first QoS requirement. The second TTI configuration comprises a second number of the OFDM symbols and is different from the first TTI configuration. The OFDM symbols with respect to the first and the second RAN slices are defined according to a single numerology. The base station informs a UE of the first and second TTI configurations mapped respectively to the first and second RAN slices.

TECHNICAL FIELD

Embodiments herein relate to wireless communication systems, such ascellular radio access networks. In particular, methods, a user equipmentand a base station in a radio access network are disclosed.Corresponding computer programs and computer program carriers are alsodisclosed.

BACKGROUND

A radio access network (RAN) covers a geographical area which is dividedinto cell areas, wherein each cell area is served by a base station. Acell is the geographical area where radio coverage is provided by thebase station at a base station site. The cells often overlap each other.One base station, situated on the base station site, may serve one orseveral cells. Further, each base station may support one or severalcommunication technologies.

A radio access network, such as a 5^(th) Generation (5G) radio accessnetwork, is supposed to support multiple types of services using commonRAN: enhanced mobile broadband (eMBB) services, massive machine typecommunication (mMTC) services and ultra-reliable and low latencycommunication (URLLC) services. These services require different Qualityof Service (QoS), including delay, data rate and packet loss rate:

-   -   URLLC services require low delay and/or high reliability, but        usually it also has very low data rate and possible sparse data        transmission;    -   mMTC services typically require long battery lifetime but does        not require low delay or high data rate, often combined with        small infrequent packets; and    -   eMBB services require high data rate. Delay can be strict but        typically less strict than in URLLC.

FIG. 1 illustrates an example of using mixed numerologies over oneCarrier Component (CC). There are two subbands, so called subband withnarrow subcarriers and subband with wide subcarriers. Owing to thedifferent numerologies used in the two subbands length of thesubcarriers in the frequency domain are different for differentsubbands, and/or length of OFDM symbols in the time domain are differentfor different subbands. In order to fulfil the delay requirement of thedifferent services, 3rd Generation Partnership Project (3GPP) RAN 1group will introduce mixed numerologies in one carrier so that theservices mentioned above may be served over one carrier. A subcarrierwidth may be 2̂n×15 kHz and the n is configurable.

Further, a so called slicing concept is being discussed in 3GPP. It willprobably be used for commercial network. The slicing concept for corenetwork is clear in 3GPP and evolving. However, how to support slicingconcept in RAN side is still being discussed. One solution is to usedifferent numerologies for different RAN slices over one carrier andenable dynamic or semi-static resource sharing between RAN slices intime-frequency domain. With such RAN slice definition, different RadioAccess Bearer (RAB), corresponding to different QoS requirement, will bemapped to proper RAN slice that may optimize the QoS fulfillment.

SUMMARY

An object may be to improve flexibility of the above mentioned radioaccess network in order to fulfill QoS requirements for various servicetypes, such as URLLC services, mMTC services, eMBB services or the like.

According to an aspect of the present disclosure, there is provided amethod performed by a base station in a Radio Access Network, RAN. Thebase station maps a first Transmission Time Interval, TTI, configurationassociated with a carrier of the RAN to a first RAN slice. The first RANslice is configured to support a first Quality of Service, QoS,requirement. The first TTI configuration comprises a first number ofOrthogonal Frequency-Division Multiplexing, OFDM, symbols. The basestation maps a second TTI configuration associated with the carrier to asecond RAN slice. The second RAN slice is configured to support a secondQoS requirement different from the first QoS requirement. The second TTIconfiguration comprises a second number of the OFDM symbols. The secondTTI configuration is different from the first TTI configuration. TheOFDM symbols with respect to the first and the second RAN slices aredefined according to a single numerology. The base station informs auser equipment, UE, of the first and second TTI configurations mappedrespectively to the first and second RAN slices.

In an embodiment, the first and the second TTI configurations correspondto at least one of: a type of the UE, the first and second QoSrequirements, and a type of a service.

In another embodiment, the informing further comprises informing the UEof a first and a second Downlink Control Information, DCI, search spacescorresponding to the first and the second RAN slices, respectively.

In yet another embodiment, the method further comprises mapping a singlesubband within the carrier to both the first and the second RAN slices.The single subband includes a number of subcarriers, and the subcarriersare defined according to said one numerology. The method also comprisesinforming the UE of the single subband mapped to the first and secondRAN slices.

In yet another embodiment, the method further comprises mapping a firstsubband within the carrier to the first RAN slice, the first subbandincluding a first number of subcarriers; and mapping a second subbandwithin the carrier to the second RAN slice, the second subband includinga second number of the subcarriers. The first subband is different fromthe second subband. The subcarriers with respect to the first and thesecond RAN slices are defined according to said one numerology. Themethod also comprises informing the UE of the first and the secondsubbands mapped to the first and second RAN slices.

In yet another embodiment, the first and the second TTI configurationscomprise a TTI length based on the number of OFDM symbols therein.Alternatively, the first and second TTI configurations comprises the TTIlength and any one of: a Downlink Control Information, DCI, searchspace; a DCI format; a Uplink Control Information, UCI, search space; aUCI format; a channel state information, CSI, measurement; a CSImeasurement report; a Status Report, SR; and a buffer status report.

According to another aspect of the present disclosure, there is provideda method performed by a user equipment, UE, for accessing a Radio AccessNetwork, RAN. The UE receives a first and a second Transmission TimeInterval, TTI, configurations mapped respectively to a first and asecond RAN slices. The first RAN slice is configured to support a firstQuality of Service, QoS, requirement. The second RAN slice is configuredto support a second QoS requirement different from the first QoSrequirement. The first TTI configuration comprises a first number ofOrthogonal Frequency-Division Multiplexing, OFDM, symbols, and isassociated with a carrier of the RAN. The second TTI configurationincludes a second number of the OFDM symbols and associates with thecarrier. The second TTI configuration is different from the first TTIconfiguration. The OFDM symbols with respect to the first and the secondRAN slices are defined according to one numerology.

According to a further aspect of the present disclosure, there isprovided a base station operable in a Radio Access Network, RAN. Thebase station comprises a first mapping module configured to map a firstTransmission Time Interval, TTI, configuration associated with a carrierof the RAN to a first RAN slice. The first RAN slice is configured tosupport a first Quality of Service, QoS, requirement. The first TTIconfiguration comprises a first number of Orthogonal Frequency-DivisionMultiplexing, OFDM, symbols. The base station comprises a second mappingmodule configured to map a second TTI configuration associated with thecarrier to a second RAN slice. The second RAN slice is configured tosupport a second QoS requirement different from the first QoSrequirement. The second TTI configuration comprises a second number ofthe OFDM symbols. The second TTI configuration is different from thefirst TTI configuration. The OFDM symbols with respect to the first andthe second RAN slices are defined according to one numerology. The basestation comprises a first informing module configured to inform a userequipment, UE, of the first and second TTI configurations mappedrespectively to the first and second RAN slices.

According to yet another aspect of the present disclosure, there isprovided a user equipment, UE, for accessing to a Radio Access Network,RAN. The UE comprises a first receiving module configured to receive afirst and a second Transmission Time Interval, TTI, configurationsmapped respectively to a first and a second RAN slices. The first RANslice is configured to support a first Quality of Service, QoS,requirement. The second RAN slice is configured to support a second QoSrequirement different from the first QoS requirement. The first TTIconfiguration comprises a first number of Orthogonal Frequency-DivisionMultiplexing, OFDM, symbols, and is associated with a carrier of theRAN. The second TTI configuration includes a second number of the OFDMsymbols and associates with the carrier. The second TTI configuration isdifferent from the first TTI configuration. The OFDM symbols withrespect to the first and the second RAN slices are defined according toone numerology.

According to further aspects of the present disclosure, computerprograms and computer program carriers corresponding to the aspectsabove are provided.

An advantage is that, compared to RAN slice definition using mixednumerologies, the embodiments herein clearly have lower complexity owingto only one numerology is employed to define the OFDM symbol in timedomain.

BRIEF DESCRIPTION OF THE DRAWINGS

The various aspects of embodiments disclosed herein, includingparticular features and advantages thereof, will be readily understoodfrom the following detailed description and the accompanying drawings,in which:

FIG. 1 is a schematic illustration of sub-bands including narrow andwide subcarriers according to prior art,

FIG. 2 is a schematic overview of an exemplifying radio access networkin which embodiments herein may be implemented,

FIG. 3 is a flowchart illustrating embodiments of the method in the basestation,

FIG. 4 is a block diagram illustrating embodiments of the base station,

FIG. 5 is a further schematic illustration of sub-bands according to anembodiment herein,

FIG. 6 is another schematic illustration of a sub-band according toanother embodiment herein,

FIG. 7 is a still other schematic illustration of a sub-band accordingto a still other embodiment,

FIG. 8 is a flowchart illustrating embodiments of the method in the userequipment, and

FIG. 9 is a block diagram illustrating embodiments of the userequipment.

DETAILED DESCRIPTION

Throughout the following description similar reference numerals havebeen used to denote similar features, such as nodes, actions, modules,circuits, parts, items, elements, units or the like, when applicable. Inthe Figures, features that appear in some embodiments are indicated bydashed lines.

As mentioned above in relation to FIG. 1, mixed numerologies forsubcarriers may be used for different sub-bands in order to supportslicing in the RAN.

When mixed numerologies are used, many technical issues need to beinvestigated: sync signal/system information design and monitoring,guard band between different numerologies, DCI search space andscheduling, filtering of mixed numerologies, random access, mobility andpower control, etc. These aspects may be discussed in 3GPP step by stepand the product development would take even longer time. Further, if RANslicing is supported by use of mixed numerologies configuration, a UEthat operates multiple services, belonging to different slices, may needto support multiple numerology operation. Considering the mentionedcomplexity of mixed numerologies, the present inventors have realizedthat a less complex but elegant solution for mixed services according toslicing concept may be achieved with the embodiments as disclosedherein.

Meeting the different delay requirement in RAN by means of mixednumerologies in one carrier requires complex standardization effort andproduction design. The embodiments herein propose methods to meet thevarious delay requirements using RAN slice definition based on TTIlength, which may be dynamically adjusted, instead of using mixednumerologies so as to avoid the complexity described above.

FIG. 2 depicts an exemplifying radio access network 100 in whichembodiments herein may be implemented.

The network 100 may be any cellular or wireless communication network,such as Long-Term Evolution (LTE), e.g. LTE Frequency Division Duplex(FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex FrequencyDivision Duplex (HD-FDD), LTE operating in an unlicensed band, or aWideband Code Division Multiple Access (WCDMA), Universal TerrestrialRadio Access (UTRA) TDD, Ultra-Mobile Broadband (UMB), Global System forMobile communications (GSM) network, GSM/Enhanced Data Rate for GSMEvolution (EDGE) Radio Access Network (GERAN) network, EDGE network, anetwork comprising of any combination of Radio Access Technologies(RATs) such as e.g. Multi-Standard Radio (MSR) base stations, multi-RATbase stations etc., any 3rd Generation Partnership Project (3GPP)cellular network, WiFi networks, Worldwide Interoperability forMicrowave Access (WiMax), 5G or New Radio (NR) system or any cellularnetwork or system.

The network 100 comprises at least one base station (BS), also referredto as access node, 110A, 110B, 110C. The base stations 110A, 110B, 110Ccommunicate over an air interface, namely cellular interface, operatingon radio frequencies with a User Equipment (UE), 120A, 120B, 120C,within range of the base stations 110A, 110B, 110C.

The UE, 120A, 120B, 120C may be a mobile terminal or a wirelessterminal, a mobile phone, a computer such as e.g. a laptop, a PersonalDigital Assistants PDAs or a tablet computer, sometimes referred to as asurf plate, with wireless capability, or any other radio network unitscapable to communicate over a radio link in a wireless communicationsnetwork. Please note that the term UE used in this document also coversother wireless devices such as Machine to machine (M2M) devices, eventhough they do not have any user.

The base station 110A, 110B, 110C may map a different Transmission TimeInterval (TTI) configuration associated with a carrier of the RAN 100 todifferent RAN slices, respectively. Each RAN slice is configured tosupport a Quality of Service (QoS) requirement. The TTI configurationsare different at different TTI lengths, which are based on a quantity ofOrthogonal Frequency-Division Multiplexing (OFDM) symbols. The OFDMsymbols with respect to all the RAN slices are defined according to asingle numerology.

The base station 110A, 110B, 110C may also be, e.g. a Radio Base Station(RBS), which sometimes may be referred to as e.g. “eNB”, “eNodeB”,“NodeB”, “B node”, gNodeB or BTS (Base Transceiver Station), dependingon the technology and terminology used. The base stations may be ofdifferent classes such as e.g. macro eNodeB, home eNodeB or pico basestation, based on transmission power and thereby also cell size.

Example of embodiments of a method performed by a base station 110A,110B, 110C will now be described with reference to FIG. 3. The basestation 110A, 110B, 110C is operable in a Radio Access Network (RAN)100.

The method may comprise the following actions, which actions may betaken in any suitable order.

Action 310

The base station 110A, 110B, 110C may map a first TTI configurationassociated with a carrier of the RAN 100 to a first RAN slice. The firstRAN slice is configured to support a first QoS requirement. The firstTTI configuration may comprise a first number of OFDM symbols.

Action 320

The base station 110A, 110B, 110C may map a second TTI configurationassociated with the carrier to a second RAN slice. The second RAN sliceis configured to support a second QoS requirement different from thefirst QoS requirement. The second TTI configuration may comprise asecond number of the OFDM symbols. The second TTI configuration may bedifferent from the first TTI configuration. As an example, at least oneof delay, data rate, packet loss rate and the like of the first andsecond QoS requirements are different.

The OFDM symbols with respect to the first and the second RAN slices maybe defined according to one numerology.

According some embodiments, the first and the second TTI configurationsmay comprise a TTI length, which is based on the number of OFDM symbolstherein; or the TTI length and any one of: a Downlink ControlInformation, DCI, search space; a DCI format; a Uplink ControlInformation, UCI, search space; a UCI format; a channel stateinformation, CSI, measurement; a CSI measurement report; a StatusReport, SR; and a buffer status report.

Action 330

The base station 110A, 110B, 110C may inform a UE 120A, 120B, 120C ofthe first and second TTI configurations mapped respectively to the firstand second RAN slices.

According to some embodiments, the first and the second TTIconfigurations may correspond to at least one of: a type of the UE, thefirst and second QoS requirements, and a type of a service.

According to some embodiments, the informing Action 330 may furthercomprise: informing the UE of a first and a second Downlink ControlInformation, DCI, search spaces corresponding to the first and thesecond RAN slices, respectively.

According to some embodiments, the informing Action 330 may be performedby using a Downlink Control Information (DCI) message.

According to some embodiments, the base station 110A, 110B, 110C mayalso map a subband to the first and the second RAN slices. Severalembodiments of mapping the subband to the first and the second RANslices will be discussed here. A first embodiment is illustrated inactions 340 and 350 and a second embodiment is illustrated in actions360. The first embodiment maps different RAN slices to differentsubbands and the second embodiment maps different RAN slices to a singlesubband.

Action 340

The base station 110A, 110B, 110C may map a first subband within thecarrier to the first RAN slice, the first subband including a firstnumber of subcarriers.

Action 350

The base station 110A, 110B, 110C may map a second subband within thecarrier to the second RAN slice. The second subband including a secondnumber of the subcarriers. The first subband is different from thesecond subband. The subcarriers with respect to the first and the secondRAN slices are defined according to said one numerology.

Action 360

The base station 110A, 110B, 110C may map a single subband within thecarrier to both the first and the second RAN slices. The single subbandincluding a number of subcarriers, wherein the subcarriers are definedaccording to said one numerology.

Action 370

The base station 110A, 110B, 110C informs the UE of the subband mappedaccording to the above mentioned first and second embodiments. Theinforming may be performed by using any known signaling, includingbroadcast signaling. The informing of the subband may be performed lowerfrequent than the informing of the TTI configuration mentioned above.

In case of the first embodiment(s), the base station 110A, 110B, 110Cinforming (370) the UE of the first and the second subbands mapped tothe first and second RAN slices. With respect to the secondembodiment(s), the base station 110A, 110B, 110C informs the UE of thesingle subband mapped to the first and second RAN slices.

Action 380

Based on the above configuration of the first and second RAN slices, thebase station 110A, 110B, 110C may transmit data having the first and thesecond QoS requirements in the first and the second RAN slices,respectively, to the UE.

To perform the method embodiments corresponding to FIG. 3, the basestation, shown as access node 110A, 110B, 110C of FIG. 2 is disclosedherein. The base station 110A, 110B, 110C may comprise the followingarrangement depicted in FIG. 4. As mentioned above, the base station110A, 110B, 110C is operable in the RAN 100.

The base station 110A, 110B, 110C is configured, e.g. by means of afirst mapping module 410, to map the first TTI configuration associatedwith the carrier of the RAN 100 to the first RAN slice.

The base station 110A, 110B, 110C is also configured, e.g. by means of asecond mapping module 420, to map the second TTI configurationassociated with the carrier of the RAN 100 to the second RAN slice.

The base station 110A, 110B, 110C is also configured, e.g. by means of afirst informing module 430, to inform the UE of the first and second TTIconfigurations mapped respectively to the first and second RAN slices.

According to some embodiments, the first informing module 430 is furtherconfigured to inform the UE of the first and the second DCI searchspaces corresponding to the first and the second RAN slices,respectively.

According to some embodiments, the first informing module 430 is furtherconfigured to inform the UE of the first and second TTI configurations,and the first and the second DCI search spaces by using the DCI message.

According to some embodiments, the base station 110A, 110B, 110C isfurther configured, e.g. by means of a third mapping module 440, to mapthe single subband within the carrier to both the first and the secondRAN slices; and e.g. by means of a second informing module 470, toinform the UE of the single subband mapped to the first and second RANslices.

According to some embodiments, the base station 110A, 110B, 110C isfurther configured, e.g. by means of a fourth mapping module 450, to mapthe first subband within the carrier to the first RAN slice; and e.g. bymeans of a fifth mapping module 460, to map the subband within thecarrier to the first RAN slice; and e.g. by means of a third informingmodule 480, to inform the UE of the first and the second subbands mappedto the first and second RAN slices.

According to some embodiments, the base station 110A, 110B, 110C isfurther configured, e.g. by means of a transmission module 490, totransmit data to or receive data from the UE in the first and second RANslices.

In some embodiments, the base station 110A, 110B, 110C may comprise aprocessing module 401, such as a means for performing the methodsdescribed herein. The means may be embodied in the form of one or morehardware modules and/or one or more software modules.

In some embodiments, the processing module 401 may comprise one or moreof the first mapping module 410, the second mapping module 420, thefirst informing module 430, the third mapping module 440, the fourthmapping 450, the fifth mapping module 460, the second informing module470, the third informing module 480, and the transmission module 490 asexemplifying hardware modules. In other examples, one or more of theaforementioned exemplifying hardware modules may be implemented as oneor more software modules.

The base station 110A, 110B, 110C may further comprise a memory 402. Thememory may comprise, such as contain or store, instructions, e.g. in theform of a computer program 403, which may comprise computer readablecode units.

According to some embodiments herein, the base station 110A, 110B, 110Cand/or the processing module 401 comprises a processing circuit 404 asan exemplifying hardware module, which may comprise one or moreprocessors. Accordingly, the processing module 401 may be embodied inthe form of, or ‘realized by’, the processing circuit 404. Theinstructions may be executable by the processing circuit 404, wherebythe base station 110A, 110B, 110C is operative to perform the methods ofFIG. 3. As another example, the instructions, when executed by the basestation 110A, 110B, 110C and/or the processing circuit 404, may causethe base station 110A, 110B, 110C to perform the method according toFIG. 3.

FIG. 4 further illustrates a computer program carrier 405, or programcarrier, which comprises the computer program 403 as described directlyabove.

Moreover, base station 110A, 110B, 110C may further comprise anInput/Output unit 406, which may be exemplified by the receiving moduleand/or the sending module as described below when applicable.

Now returning to the first embodiment, in which an explicit RAN slicedefinition is provide by use of different TTI lengths for differentsubbands within the carrier.

According to these embodiments, one carrier may be divided into morethan one subband, where all subcarriers in said more than one subbandhave the same numerology. Each subband may comprise different number ofsubcarriers or the same number, as shown in FIG. 5, and differentsubbands are configured to different TTI lengths. The TTI length is thusgiven by a number of OFDM symbols included in the TTI. Each subband maybe regarded as one RAN slice in this case. This means that each subbandis associated with a respective RAN slice, where the respective RANslice supports services having a certain QoS requirement. FIG. 5illustrates one example. In the figure, there are Subband 1 and 2, whichare configured to TTI type 1 and 2 respectively. TTI types 1 and 2 have7 and 2 Orthogonal Frequency-Division Multiplexing (OFDM) symbolsrespectively. Subband 1 may support high data rate for eMBB services andSubband 2 may support high reliability and low delay services. There areseparate resource pools for Downlink Control Information (DCI)transmission for different subbands. UE specific DCI search space isallocated from the respective resource pool for DCI transmission.

As mentioned above, the second TTI configuration may be different fromthe first TTI configuration. As an example, the first number of OFDMsymbols is different from the second number of OFDM symbols. Thus, thefirst and second TTI configurations differ from each other.

The first subband is different from the second subband by havingdifferent number of subcarriers, by having different frequencies, orboth. For instance, different sub-bands may be not overlap, and maycomprise different number of the subcarriers defined by the single onenumerology.

According to some embodiments, the method further comprises configuringa same Demodulation Reference Signal, DRS, signal, and/or a same randomaccess procedure for both the first and second sub-bands.

As an example, this means that different subbands may have sharedDemodulation reference signal (DRS) signals such as sync signal andmandatory system information transmission. The UEs served by differentsubbands may monitor the same DRS signal for mobility management.

According to some embodiments, the method further comprises configuringthe following sub-band specific parameters with respect to at least oneof the first and second sub-bands for each sub-band: Downlink ControlInformation search space, Downlink Control Information format, transportformat table, scheduling scheme, Channel State Information, CSI,measurement and report, Uplink Control Information format, UplinkControl Information transmission and resource mapping, timing for uplinkscheduling.

As an example, each subband has respective DCI search spaceconfigurations. Since typically there is one search space in each TTI,it is impossible to share the DCI search space configuration betweendifferent subbands with different TTI lengths.

As an example, different subbands may have different resourcegranularity configurations. For instance, one PRB may include 12subcarriers in subband 1 and 6 subcarriers for subband 2.

As an example, each subband may be configured with specific transportformat table. For instance, for URLLC traffic, it is not so promising tohave high order modulation, high coding rate or high rank transmissioncompared to eMBB traffic. More, since there may be high probability ofsmall packet transmission, it is beneficial to improve the TB sizegranularity for RAN slice for small packets for URLLC services.

As an example, each subband has specific DCI format configuration.Taking into consideration of the above embodiments, the DCI format fordifferent subbands may be separately configured for each UE.

As an example, scheduling scheme for different subband may be configuredrespectively. As one example, multiple subframe scheduling may beconfigured for subband 1 for eMBB traffic while not configured forsubband 2 for URLLC traffic. As one more example, proportional fairscheduling scheme may be configured for Subband 1 while delay criticalscheduling scheme may be configured for subband 2.

Channel state information (CSI) measurement and report for differentsubband may be separately configured. Thus, for subband 1 to provide MBBservices, the UE may be configured to evaluate the rank, precodingmatrix and the CQI for each stream. For subband 2 to provide URLLCservices, one would probably always use Rank 1 transmission, the TRP mayconfigure the UE to evaluate the precoding matrix and CQI only.

Uplink Control Information (UCI) format, transmission and resourcemapping may be subband specific. Hence, since the data transmissionscheme, scheduling scheme and data rate for services operated indifferent subbands are very different, the time and frequency resourcesto send the scheduling request, the number of HARQ A/N bits, the time tosend the HARQ feedback, the number of CSI bits and the time to send theCSI report are quite different for different subbands. Hence differentUCI configurations are needed for different subbands. It is desired toconfigure the UCI format, transmission and resource mapping fordifferent subbands respectively.

As an example, timing for uplink scheduling may be subband specific.This may mean that the time from SR receiving to UL grant transmissionand the time from UL grant transmission from UL grant receiving to ULdata transmission may be different and separately configured fordifferent subbands because of the TTI length difference.

As an example, a common random access procedure may be used for UEs toaccess different subbands. This may imply that a default TTI length maybe predefined and any UE may access the network via common random accessprocedure and then switch to preferred subband according to the UE typeor traffic type.

Turning to the second embodiment mentioned above, explicit RAN slicedefinition is achieved by use of different TTI lengths within the samesubband.

According to these embodiments, RAN slices are mapped to different TTIlength as with the first embodiment, but the RAN slices are multiplexedin the same subband. This setup has the advantage that the size, i.e.number of resources used by the RAN slice, of the RAN slice maydynamically be changed. This embodiment provides for how to handle iftime-frequency resources occupied by an already ongoing transmission 1,in a “long TTI” RAN slice, suddenly are now needed for an urgenttransmission 2 in a “short TTI” RAN slice. In this context, the terms“long” and “short” are relatively each other with respect to number ofOFDM symbols in the TTIs of the respective RAN slices. Due to theurgency of the transmission 2 obviously transmission 2 overwritestransmission 1 in the colliding resources. Solutions to mitigate theimpact on transmission 1 are to send a signal to receiver oftransmission 1 indicating the puncturing, special coding solutions suchas outer codes, or re-transmission schemes. With respect to theembodiments above, the TTI length and the associated parameters may beconfigured for a UE according to the UE type or the traffic type for theUE. As an example, UE 1 requesting a delay critical service isconfigured to short TTI length with 2 OFDM symbols; while UE 2requesting the eMBB services is configured to TTI length with 7 OFDMsymbols.

According to the embodiments above, TTI configuration may be performedin a static way, a dynamic way or both.

Option 1: UE specific Static TTI length configuration, also referred toas TTI length schedule according to UE type or traffic type

As one option, the informing Action 340 is performed by using at leastone of: a Radio Resource Control message, a MAC Control Element, and aDownlink Control Information.

For this option, the TTI length and the associated parameters may beconfigured for a UE according to the UE type or the traffic type for theUE by using a Radio Resource Control (RRC) message or MAC ControlElement (MAC CE). The associated parameters includes a DCI search spaceand format, a UCI search space and format, a CSI measurement and reportparameters, a Status Report (SR) and buffer status report parametersetc. The configuration can be finished during the session setupprocedure for a UE according to the UE or traffic type. As one example,UE 1 requesting a delay critical service is configured to short TTIlength with 2 OFDM symbols; while UE 2 requesting the eMBB services isconfigured to TTI length with 7 OFDM symbols.

FIG. 6 shows the example of RAN slice definition using TTI length andsame subband, UE specific TTI length configuration and a correspondingDCI search space. UE1 with eMBB service uses long TTI length while UE 2with delay critical services uses short TTI length.

Option 2: dynamic scheduled TTI configuration length using DCI

As another option, the informing Action 340 is performed by using DCImessage which is in a new format proposed by the disclosure.

For this option, the TTI length for a UE is dynamically configured usingDCI command/message. Specific DCI format to indicate the TTI length andthe specific DCI search space for the specific DCI transmission may beconfigured for UE. After the UE decodes the DCI, the UE knows the TTIlength and performs the data decoding according to the determined TTIlength. The DCI format configuration informs the UE whether the flexibleTTI length is applied for the UE or not. For dynamic scheduled TTIlength, the DCI search space occurrences may be configured according tothe short TTI length so that each short TTI may have at least one DCIsearch space occurrence.

In some examples, DCI search space configuration is notified to and usedby the UE. FIG. 6 further illustrates an example of a DCI search spaceconfiguration with respect to dynamic scheduled RAN slice TTI length,the DCI search space occurrences may be configured according to theshort TTI length so that each short TTI may have at least one DCI searchspace occurrence. As shown in FIG. 6, UE 1 uses DCI search space foreMBB service, shown as striped DCI, and UE 2 uses DCI search space, fordelay critical service, shown as meshed DCI.

FIG. 7 shows another example of a DCI search space configuration examplefor with respect to dynamic scheduled RAN slice for UE 1 with dynamicTTI length. In this figure, there is a shared DCI search space whenthere is aligned TTI boundary. The DCI search space occurrence for shortTTI scheduling is more frequent. As an example shown in FIG. 6, for thefirst RAN slice, shown as long TTI length in the figure, where M=7*OFDM,the DCI search space occurrence is 7. For the second RAN slice, shown asshort TTI length in the figure, where N=2*OFDM, the DCI search spaceoccurrence is 2.

Compared to option 1, the TTI length adaptation is more dynamical. Thisalso put certain requirement on the signaling processing in the UE sidedue to TTI length change also means that the signal processing for datareceiving may be adapted accordingly.

Option 3: A combination of the above Static and dynamic TTIconfiguration, which is also referred to as “semi-static TTIconfiguration”. In this case, the TTI may begin with the Static TTIconfiguration, then dynamically updated according to the dynamic TTIconfiguration.

Example of embodiments of a method performed by the user equipment, UE,120A, 120B, 120C for accessing to a Radio Access Network (RAN) 100 willnow be described with reference to FIG. 8.

The method may comprise the following actions, which actions may betaken in any suitable order.

Action 810

The UE 120A, 120B, 120C may receive the first and the second TTIconfigurations mapped respectively to the first and the second RANslices, from the base station. As the first and the second TTIconfigurations, and the first and the second RAN slices have beendiscussed in the embodiment corresponding to FIG. 3, they will not berepeated again.

In case the informing Action 330 performed by the base station is doneby the DCI message, the receiving Action 810 is performed by using theDCI message accordingly.

With respect to subband, corresponding to the base station 110A, 110B,110C embodiment, the UE 120A, 120B, 120C may receive an indication ofthe subband mapped to the first and the second RAN slices. Severalalternatives of receiving the subband mapped to the first and the secondRAN slices will be discussed here.

In case of the base station maps different RAN slices to a singlesubbands, Action 820 as follows will be performed.

Action 820

The UE 120A, 120B, 120C may receive an indication of the above singlesubband within the carrier mapped to both the first and the second RANslices.

In case the base station maps different RAN slices to differentsubbands, following Actions 830 and 840 will be performed.

Action 830

The UE 120A, 120B, 120C may receive an indication of the above firstsubband within the carrier mapped to the first RAN slice.

Action 840

The UE 120A, 120B, 120C may receive an indication of the above secondsubband within the carrier mapped to the second RAN slice.

Action 850

According to some embodiment, the UE 120A, 120B, 120C may search the DCIin the DCI search space, which will be discussed in FIGS. 6 and 7.

Action 860

After knowing the first and the second RAN slice, the UE 120A, 120B,120C may transmit data to or receive data from base station in the firstand second RAN slices.

In view of the above, the following further embodiments relating to theUE may be contemplated.

As an embodiment, the UE may receive the configured RAN sliceconfiguration, including TTI configuration, subband bandwidth andmeasurement configuration from the network and selects the RAN slice forservice providing according to the UE type or the type of service basedon predefined rules.

As another embodiment, the UE may report the UE type to the network, andthe UE determine the slice to be used based on a set of parametersreceived from the network including the subband bandwidth, the TTIconfiguration and measurement configurations.

As one further embodiment, when the UE is served by more than one RANslice, one measurement and/or report configuration may be shared by themore than one RAN slice.

As a further embodiment, when dynamical flexible TTI length isconfigured for a UE, the UE may be configured to use new DCI format inwhich the TTI length indicator is carried.

As a further embodiment, when dynamical flexible TTI length isconfigured for a UE being served by a RAN slice, the UE may beconfigured to monitor each DCI search space respectively for each RANslice.

As a further embodiment, when dynamical flexible TTI length isconfigured for a UE being served by a RAN slice, the UE may beconfigured to monitor joint DCI search space for different TTI length.

As a further embodiment, when dynamical flexible TTI length isconfigured for a UE being served by a RAN slice, the UE may beconfigured to one measurement and measurement report configurationirrespective of TTI length.

As a further embodiment, when dynamical flexible TTI length isconfigured for a UE being served by a RAN slice, the UE may beconfigured to one measurement and measurement report configurationsaccording to the shortest TTI length.

To perform the method embodiments corresponding to FIG. 8, the UE 120A,120B, 120C of FIG. 2 is shown is discussed herein. The UE 120A, 120B,120C may comprise the following arrangement depicted in FIG. 9 foraccessing the RAN 100.

The UE 120A, 120B, 120C is configured, e.g. by means of a firstreceiving module 910, to receive the first and the second TTIconfigurations mapped respectively to the first and the second RANslices.

According to some embodiments, the first receiving module 910 is furtherconfigured to receive the first and the second DCI search spacescorresponding to the first and the second RAN slices, respectively.

According to some embodiments, the first receiving module 910 is furtherconfigured to: receive the first and second TTI configurations, and thefirst and the second DCI search spaces by using the DCI message.

According to some embodiments, the UE 120A, 120B, 120C is furtherconfigured, e.g. by means of a second receiving module 920, to receivethe indication of a single subband within the carrier mapped to both thefirst and the second RAN slices.

According to some embodiments, the UE 120A, 120B, 120C is furtherconfigured, e.g. by means of a third receiving module 930, to receivethe indication of a first subband within the carrier mapped to the firstran slice; and e.g. by means of a fourth receiving module 940, toreceive the indication of a second subband within the carrier mapped tothe second RAN slice.

According to some embodiments, the UE 120A, 120B, 120C is furtherconfigured, e.g. by means of a searching module 950, to search the DCIaccording to the DCI search spaces.

According to some embodiments, the UE 120A, 120B, 120C is furtherconfigured, e.g. by means of a transmission module 960, to transmit datato or receive data from the base station according to the RAN slices, inorder to meet different QoS requirements from the services.

In some embodiments, the UE 120A, 120B, 120C may comprise a processingmodule 901, such as a means for performing the methods described herein.The means may be embodied in the form of one or more hardware modulesand/or one or more software modules.

In some embodiments, the processing module 901 may comprise one or moreof the first receiving module 910, the second receiving module 920, thethird receiving module 930, the fourth receiving module 940, thesearching module 950, and the transmission module 960 as exemplifyinghardware modules. In other examples, one or more of the aforementionedexemplifying hardware modules may be implemented as one or more softwaremodules.

The UE 120A, 120B, 120C may further comprise a memory 902. The memorymay comprise, such as contain or store, instructions, e.g. in the formof a computer program 903, which may comprise computer readable codeunits.

According to some embodiments herein, the UE 120A, 120B, 120C and/or theprocessing module 901 comprises a processing circuit 904 as anexemplifying hardware module, which may comprise one or more processors.Accordingly, the processing module 901 may be embodied in the form of,or ‘realized by’, the processing circuit 904. The instructions may beexecutable by the processing circuit 904, whereby the UE 120A, 120B,120C is operative to perform the methods of FIG. 8. As another example,the instructions, when executed by the UE 120A, 120B, 120C and/or theprocessing circuit 904, may cause the UE 120A, 120B, 120C to perform themethod according to FIG. 8.

FIG. 9 further illustrates a computer program carrier 905, or programcarrier, which comprises the computer program 903 as described directlyabove.

Moreover, UE 120A, 120B, 120C may further comprise an Input/Output unit906, which may be exemplified by the receiving module and/or the sendingmodule as described below when applicable.

Network slicing consists of deploying multiple end-to-end logicalnetworks in support of independent business operations. In contrast todeploying an independent network infrastructure, each instance of aslice (blueprint) should be possible to realize as a logical networkcorresponding to a shared infrastructure (including shared processing,storage, transport, radio spectrum, and hardware platforms), where itco-exists with other slices having potentially differentcharacteristics.

In this way, the infrastructure and assets utilization will be much morecost and energy efficient while the logical separation allows for aflexible and independent configuration and management of the sliceswithout compromising stability and security. Enabling slice realizationover a common physical infrastructure would of course not prevent therealization of a slice instance by means of dedicated resources andassets.

As used herein, the term “node”, or “network node”, may refer to one ormore physical entities, such as devices, apparatuses, computers, serversor the like. This may mean that embodiments herein may be implemented inone physical entity. Alternatively, the embodiments herein may beimplemented in a plurality of physical entities, such as an arrangementcomprising said one or more physical entities, i.e. the embodiments maybe implemented in a distributed manner, such as on a set of servermachines of a cloud system.

As used herein, the term “module” may refer to one or more functionalmodules, each of which may be implemented as one or more hardwaremodules and/or one or more software modules and/or a combinedsoftware/hardware module in a node. In some examples, the module mayrepresent a functional unit realized as software and/or hardware of thenode.

As used herein, the term “computer program carrier”, “program carrier”,or “carrier”, may refer to one of an electronic signal, an opticalsignal, a radio signal, and a computer readable medium. In someexamples, the computer program carrier may exclude transitory,propagating signals, such as the electronic, optical and/or radiosignal. Thus, in these examples, the computer program carrier may be anon-transitory carrier, such as a non-transitory computer readablemedium.

As used herein, the term “processing module” may include one or morehardware modules, one or more software modules or a combination thereof.Any such module, be it a hardware, software or a combinedhardware-software module, may be a determining means, estimating means,capturing means, associating means, comparing means, identificationmeans, selecting means, receiving means, sending means or the like asdisclosed herein. As an example, the expression “means” may be a modulecorresponding to the modules listed above in conjunction with theFigures.

As used herein, the term “software module” may refer to a softwareapplication, a Dynamic Link Library (DLL), a software component, asoftware object, an object according to Component Object Model (COM), asoftware component, a software function, a software engine, anexecutable binary software file or the like.

The terms “processing module” or “processing circuit” may hereinencompass a processing unit, comprising e.g. one or more processors, anApplication Specific integrated Circuit (ASIC), a Field-ProgrammableGate Array (FPGA) or the like. The processing circuit or the like maycomprise one or more processor kernels.

As used herein, the expression “configured to/for” may mean that aprocessing circuit is configured to, such as adapted to or operative to,by means of software configuration and/or hardware configuration,perform one or more of the actions described herein.

As used herein, the term “action” may refer to an action, a step, anoperation, a response, a reaction, an activity or the like. It shall benoted that an action herein may be split into two or more sub-actions asapplicable. Moreover, also as applicable, it shall be noted that two ormore of the actions described herein may be merged into a single action.

As used herein, the term “memory” may refer to a hard disk, a magneticstorage medium, a portable computer diskette or disc, flash memory,random access memory (RAM) or the like. Furthermore, the term “memory”may refer to an internal register memory of a processor or the like.

As used herein, the term “computer readable medium” may be a UniversalSerial Bus (USB) memory, a DVD-disc, a Blu-ray disc, a software modulethat is received as a stream of data, a Flash memory, a hard drive, amemory card, such as a MemoryStick, a Multimedia Card (MMC), SecureDigital (SD) card, etc. One or more of the aforementioned examples ofcomputer readable medium may be provided as one or more computer programproducts.

As used herein, the term “computer readable code units” may be text of acomputer program, parts of or an entire binary file representing acomputer program in a compiled format or anything there between.

As used herein, the term “radio resource” or “resource” may refer to acertain coding of a signal and/or a time frame and/or a frequency rangein which the signal is transmitted. In some examples, a resource mayrefer to one or more Physical Resource Blocks (PRB) which is used whentransmitting the signal. In more detail, a PRB may be in the form ofOrthogonal Frequency Division Multiplexing (OFDM) PHY resource blocks(PRB). The term “physical resource block” is known from 3GPP terminologyrelating to e.g. Long Term Evolution Systems.

As used herein, the expression “transmit” and “send” are considered tobe interchangeable. These expressions include transmission bybroadcasting, unicasting, group-casting and the like. In this context, atransmission by broadcasting may be received and decoded by anyauthorized device within range. In case of unicasting, one specificallyaddressed device may receive and decode the transmission. In case ofgroup-casting, a group of specifically addressed devices may receive anddecode the transmission.

As used herein, the terms “number” and/or “value” may be any kind ofdigit, such as binary, real, imaginary or rational number or the like.Moreover, “number” and/or “value” may be one or more characters, such asa letter or a string of letters. “Number” and/or “value” may also berepresented by a string of bits, i.e. zeros and/or ones.

As used herein, the term “set of” may refer to one or more of something.E.g. a set of devices may refer to one or more devices, a set ofparameters may refer to one or more parameters or the like according tothe embodiments herein.

As used herein, the expression “in some embodiments” has been used toindicate that the features of the embodiment described may be combinedwith any other embodiment disclosed herein.

Further, as used herein, the common abbreviation “e.g.”, which derivesfrom the Latin phrase “exempli gratia,” may be used to introduce orspecify a general example or examples of a previously mentioned item,and is not intended to be limiting of such item. If used herein, thecommon abbreviation “i.e.”, which derives from the Latin phrase “idest,” may be used to specify a particular item from a more generalrecitation. The common abbreviation “etc.”, which derives from the Latinexpression “et cetera” meaning “and other things” or “and so on” mayhave been used herein to indicate that further features, similar to theones that have just been enumerated, exist.

Even though embodiments of the various aspects have been described, manydifferent alterations, modifications and the like thereof will becomeapparent for those skilled in the art. The described embodiments aretherefore not intended to limit the scope of the present disclosure.

1. A method performed by a base station in a Radio Access Network (RAN),the method comprising: mapping a first Transmission Time Interval (TTI)configuration associated with a carrier of the RAN to a first RAN slice,wherein the first RAN slice is configured to support a first Quality ofService (QoS) requirement, wherein the first TTI configuration comprisesa first number of Orthogonal Frequency-Division Multiplexing (OFDM)symbols; mapping a second RAN slice, wherein the second RAN slice isconfigured to support a second QoS requirement different from the firstQoS requirement, wherein the second TTI configuration comprises a secondnumber of the OFDM symbols, wherein the second TTI configuration isdifferent from the first TTI configuration; wherein the OFDM symbolswith respect to the first and the second RAN slices are definedaccording to one numerology; and informing a user equipment (UE) of thefirst and second TTI configurations mapped respectively to the first andsecond RAN slices.
 2. The method according to claim 1, wherein the firstand the second TTI configurations correspond to at least one of: a typeof the UE, the first and second QoS requirements, and a type of aservice.
 3. The method according to claim 1, wherein the informingfurther comprises: informing the UE of a first and a second DownlinkControl Information (DCI) search spaces corresponding to the first andthe second RAN slices, respectively.
 4. The method according to claim 1,wherein the informing is performed by using a Downlink ControlInformation (CDI) message.
 5. The method according to claim 1, whereinthe method further comprises: mapping a single subband within thecarrier to both the first and the second RAN slices, the single subbandincluding a number of subcarriers, wherein the subcarriers are definedaccording to said one numerology; and informing the UE of the singlesubband mapped to the first and second RAN slices.
 6. The methodaccording to claim 1, wherein the method further comprises: mapping afirst subband within the carrier to the first RAN slice, the firstsubband including a first number of subcarriers; mapping a secondsubband within the carrier to the second RAN slice, the second subbandincluding a second number of the subcarriers, wherein the first subbandis different from the second subband; wherein the subcarriers withrespect to the first and the second RAN slices are defined according tosaid one numerology; and informing the UE of the first and the secondsubbands mapped to the first and second RAN slices.
 7. The methodaccording to claim 1, wherein the first and the second TTIconfigurations comprise: a TTI length based on the number of OFDMsymbols therein; or the TTI length and any one of: a Downlink ControlInformation (DCI) search space; a DCI format; a Uplink ControlInformation (UCI) search space; a UCI format; a channel stateinformation (CSI) measurement; a CSI measurement report; a Status Report(SR); and a buffer status report.
 8. A method performed by a userequipment (UE) for accessing a Radio Access Network (RAN), the methodcomprising: receiving a first and a second Transmission Time Interval(TTI) configurations mapped respectively to a first and a second RANslices; wherein the first RAN slice is configured to support a firstQuality of Service (QoS) requirement, the second RAN slice is configuredto support a second QoS requirement different from the first QoSrequirement; wherein the first TTI configuration comprises a firstnumber of Orthogonal Frequency-Division Multiplexing (OFDM) symbols, andis associated with a carrier of the RAN; wherein the second TTIconfiguration includes a second number of the OFDM symbols andassociates with the carrier, wherein the second TTI configuration isdifferent from the first TTI configuration; and wherein the OFDM symbolswith respect to the first and the second RAN slices are definedaccording to one numerology.
 9. The method according to claim 8, whereinthe first and the second TTI configurations correspond to at least oneof: a type of the UE, the first and second QoS requirements, and a typeof a service.
 10. The method according to claim 8, wherein receivingfurther comprises: receiving a first and a second Downlink ControlInformation (DCI) search spaces corresponding to the first and thesecond RAN slices, respectively.
 11. The method according to claim 8,wherein the receiving is performed by using a Downlink ControlInformation (DCI) message.
 12. The method according to claim 8, whereinthe method further comprises: receiving an indication of a singlesubband within the carrier mapped to both the first and the second RANslices, the single subband including a number of subcarriers, whereinthe subcarriers are defined according to said one numerology.
 13. Themethod according to claim 8, wherein the method further comprises:receiving an indication of a first subband within the carrier mapped tothe first RAN slice, the first subband including a first number ofsubcarriers; and receiving an indication of a second subband within thecarrier mapped to the second RAN slice, the second subband including asecond number of the subcarriers, wherein the first subband is differentfrom the second subband; wherein the subcarriers with respect to thefirst and the second RAN slices are defined according to said onenumerology.
 14. The method according to claim 8, wherein the first andthe second TTI configurations comprise: a TTI length based on the numberof OFDM symbols therein; or the TTI length and any one of: a DownlinkControl Information (DCI) search space; a DCI format; a Uplink ControlInformation (UCI) search space; a UCI format; a channel stateinformation (CSI) measurement; a CSI measurement report; a Status Report(SR); and a buffer status report.
 15. A base station operable in a RadioAccess Network (RAN), the base station comprising: a processor; a memorycoupled to the processor, the memory containing instructions, which whenexecuted by the processor, cause the base station to: map a firstTransmission Time Interval (TTI) configuration associated with a carrierof the RAN to a first RAN slice, wherein the first RAN slice isconfigured to support a first Quality of Service (QoS) requirement,wherein the first TTI configuration comprises a first number ofOrthogonal Frequency-Division Multiplexing (OFDM) symbols; map a secondTTI configuration associated with the carrier to a second RAN slice,wherein the second RAN slice is configured to support a second QoSrequirement different from the first QoS requirement, wherein the secondTTI configuration comprises a second number of the OFDM symbols, whereinthe second TTI configuration is different from the first TTIconfiguration; wherein the OFDM symbols with respect to the first andthe second RAN slices are defined according to one numerology; andinform a user equipment (UE) of the first and second TTI configurationsmapped respectively to the first and second RAN slices.
 16. The basestation according to claim 15, wherein the instructions, which whenexecuted by the processor, further cause the base station to: inform theUE of a first and a second Downlink Control Information (DCI) searchspaces corresponding to the first and the second RAN slices,respectively.
 17. (canceled)
 18. The base station according to claim 15,wherein the instructions, which when executed by the processor, furthercause the base station to: map a single subband within the carrier toboth the first and the second RAN slices, the single subband including anumber of subcarriers, wherein the subcarriers are defined according tosaid one numerology; and inform the UE of the single subband mapped tothe first and second RAN slices.
 19. The base station according to claim15, wherein the instructions, which when executed by the processor,further cause the base station to: map a first subband within thecarrier to the first RAN slice, the first subband including a firstnumber of subcarriers; map a second subband within the carrier to thesecond RAN slice, the second subband including a second number of thesubcarriers, wherein the first subband is different from the secondsubband; wherein the subcarriers with respect to the first and thesecond RAN slices are defined according to said one numerology; andinform the UE of the first and the second subbands mapped to the firstand second RAN slices.
 20. A user equipment (UE) for accessing to aRadio Access Network (RAN), comprising: a processor; and a memorycoupled to the processor, the memory containing instructions, which whenexecuted by the processor, cause the UE to: receive a first and a secondTransmission Time Interval (TTI) configurations mapped respectively to afirst and a second RAN slices; wherein the first RAN slice is configuredto support a first Quality of Service, QoS, requirement, the second RANslice is configured to support a second QoS requirement different fromthe first QoS requirement; wherein the first TTI configuration comprisesa first number of Orthogonal Frequency-Division Multiplexing (OFDM)symbols, and is associated with a carrier of the RAN; wherein the secondTTI configuration includes a second number of the OFDM symbols andassociates with the carrier, wherein the second TTI configuration isdifferent from the first TTI configuration; and wherein the OFDM symbolswith respect to the first and the second RAN slices are definedaccording to one numerology.
 21. The UE according to claim 20, whereinthe instructions, which when executed by the processor, further causethe UE to: receive a first and a second Downlink Control Information(DCI) search spaces corresponding to the first and the second RANslices, respectively.
 22. (canceled)
 23. The UE according to claim 20,wherein the instructions, which when executed by the processor, furthercause the UE to: receive an indication of a single subband within thecarrier mapped to both the first and the second RAN slices, the singlesubband including a number of subcarriers, wherein the subcarriers aredefined according to said one numerology.
 24. The UE according to claim20, wherein the instructions, which when executed by the processor,further cause the UE to: receive an indication of a first subband withinthe carrier mapped to the first RAN slice, the first subband including afirst number of subcarriers; and receive an indication of a secondsubband within the carrier mapped to the second RAN slice, the secondsubband including a second number of the subcarriers, wherein the firstsubband is different from the second subband; wherein the subcarrierswith respect to the first and the second RAN slices are definedaccording to said one numerology. 25-28. (canceled)